Custom Query (1174 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:

Results (271 - 273 of 1174)

← 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 →
Ticket Resolution Summary Owner Reporter
#166 FIXED Custom grid generator Karen Rustad Jef van Schendel
Description

We'll need to build a custom grid generator to get some decent thumbnail grids.

Here's what we have in mind now:

  • It should be able to create grids of different sizes, so we can choose different amounts of columns and rows.
  • Each thumbnail will be in a div element.
  • Every row of thumbnails will also be in a div. This will allow the rows to resize according to their contents (say a row only contains very wide images, in that case the height will be lower to avoid awkward spacing).
  • Each of these elements will have a class. For correct margins, the first and last thumbnail element in every row will have a second class that removes the margin at the left or right side, respectively.
  • The same should probably be true for the first and last row, to avoid extra space at the bottom or top of the grid.

(As I understand it, correct me if I'm wrong.)

So, basically like cwebber said:

<div class="thumb_gallery">
   <div class="thumb_row">
     <div class="thumb_entry">
       <div class="thumb_image">
         <img src="blabla" />
       </div>
       <div class="thumb_label">Bla bla</div>
     [...]

And then for instance a thumbnail element will looks like:

<div class="thumb_entry">

While a thumbnail element on the far right would have an extra class:

<div class="thumb_entry thumb_last">

Probably not important, but for reference: we're using thumbnails that are 180px wide, with 10px of space in between.
#892 duplicate Data liberation Jessica Tallon
Description

It would be really awesome if you were able to easily export all your data from Mediagoblin and have all the media you uploaded put into a tar/zip/whatever that you can download. It would also be useful if some of the user data (name, description, etc.) was exported so if someone was going to deploy their own Mediagoblin instance or move from an existing deployment they could just import the tar/zip/etc. file.

#679 fixed Database "fixtures" (but not the testing kind) Christopher Allan Webber
Description

(Note: this is *not* the best name, because it could be confused with unit testing fixtures... I don't know if there's a better name that does not have that overlap.)

We're using a relational database, and this means there may be expectations that certain rows are installed in tables. This could be for several reasons:

  • we might have a table that contains different license options; by default, we would want to prepopulate with some good ones
  • we might store permissions in the database with certain roles, such as in #678. But in order to check if someone is in the admin group, that group would need to already exist!
  • maybe we could stop storing media type information on media models as a string! Instead, we could have media types like images, video, etc, on a table. But that also means that every time we install a media type it needs to set up a fixture in the application for itself.

As far as I can tell, installing fixtures will happen in a couple of ways:

  • The first time that mediagoblin core or an extension such as a plugin/media type is installed, it will need to set up some common fixtures. We need new tooling for this!
  • Later, new fixtures may be added or changed. This is easy; we do not need a new tooling for this, we can use our existing migrations infrastructure.

So in theory, the above two can be handled both by ./bin/gmg dbupdate... we just need to add new tooling for the former.

(There's one more possibile tool we could add to this: a convenience method that queries for a certain row, and if it doesn't see it, creates it. That's not super necessary though.)

← 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 →
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.