- Development - lists.drupal.org

Re: [bug] Allow embedded images in project description
by David Reed 09 Mar '06

09 Mar '06

I've updated this issue with a new patch that adds a new "preview_url" field to store a screenshot image url. This patch also provides for using the existing screenshots field to show a "more previews" type link. On 3/6/06, Dries <drupal-devel(a)drupal.org> wrote: > > Issue status update for > http://drupal.org/node/49575 > Post a follow up: > http://drupal.org/project/comments/add/49575 > > Project: Project > Version: cvs > Component: User interface > Category: bug reports > Priority: normal > Assigned to: Anonymous > Reported by: der > Updated by: Dries > Status: patch (code needs review) > > Code comment: we should wrap a check_url() around the screenshot URL > (depending on the format). We should add an alt-attribute for level 1 > accessibility. > > > What happens with projects who configured a screenshot link? The > Drupal project's screenshot link, for example, points to a gallery (see > http://drupal.org/project/drupal) Maybe we need to add a second URL so > we can do stuff like they do at the Firefox plugin directory (see > > https://addons.mozilla.org/extensions/moreinfo.php?id=220&application=firef… > and note the 'more previews' link below the screenshot). > > > Would you be able to work on this some more, so we can implement this > properly? I'd be happy to help test/review such functionality and roll > it out on drupal.org. > > > > > Dries > > > > Previous comments: > ------------------------------------------------------------------------ > > Wed, 15 Feb 2006 21:09:41 +0000 : der > > Per the related discussion [1] on the infrastructure mailing list, there > needs to be a way to embed an image in the description of a project. > This is particularly useful for showing theme screenshots. > [1] > http://lists.drupal.org/archives/infrastructure/2006-02/msg00154.html > > > > > ------------------------------------------------------------------------ > > Sat, 04 Mar 2006 05:35:47 +0000 : der > > Attachment: http://drupal.org/files/issues/project.module_1.patch (1.69KB) > > Here's a patch that uses the existing screenshots db field for the img > tag source. > > > > > ------------------------------------------------------------------------ > > Mon, 06 Mar 2006 15:09:14 +0000 : der > > Just a comment on this patch. The intent of this feature request was to > allow screenshot images to be displayed for "theme" projects. But the > patch doesn't limit it to any particular project type. My assumption > is that it could be controlled in the stylesheet. > > > > >

1 0

Error: Cannot create references to/from string offsets nor overloaded objects
by Karoly Negyesi 09 Mar '06

09 Mar '06

Hi! Form properties, their name beginning with a # , can be of any type. However, if there is no #, it's a child and it must be an array. If it's not, you'll get "Cannot create references to/from string offsets nor overloaded objects". If you get this error, you missed a #. If you an issue filed with this it's very probable that it's a contrib module not yet form API'd or a bogus module. Regards NK

1 0

Updated spellcheck module - now what
by Will Wyatt 09 Mar '06

09 Mar '06

Hi all. I've completly rewritten the old 4.5 spellcheck module. I'm about ready to 'release' the module and wonder what I'm supposed to do now. I could create a patch, but there is almost nothing that remains from the old spellcheck module. This is also my first module for Drupal, so I'm hoping I've done everything correctly. So, what should I do now? The module uses the GPL'ed Speller Pages from http://spellerpages.sourceforge.net and requires aspell on the server. You can try it out at http://test.willwyatt.com you can login as testuser/testuser and create a blog entry. There should be a 'Check Spelling' button below the body form element. The module only works with 4.7 and has only been tested against 4.7 CVS. The module really is just a front end to aspell, so your mileage may vary depending on your aspell installation. Code is available http://www.willwyatt.com/files/spellcheck.tar.gz I guess if the code meets requirements I'd like to be the maintainer of the new module. -- Proud member of the KEXP cubicle army. http://www.cubiclearmy.com

3 3

floating resource
by Urbits - Info 09 Mar '06

09 Mar '06

I am about to do a clean install on my test server (php5). I'm available to test code for the next 2-3 hours. Email me or reply here with links as appropriate.

2 2

crazy request: solidarity
by Dries Buytaert 09 Mar '06

09 Mar '06

I'm the first person to acknowledge that working on Drupal should be fun and that you should work on aspects of the code that you think are particularly interesting or rewarding. However, the current focus is clear: getting Drupal 4.7.0 out. As a result, some of us have dropped all the 'fun Drupal things' to focus solely on getting the Drupal 4.7.0 release out. I, for one, haven't worked on new features for months. At the same time, many people have been working on their pet projects. See, those who are committed to getting Drupal 4.7.0 out want to pick up their pet projects too ... We're getting to a point where solidarity becomes absolutely indispensable and to focus on the greater good: getting Drupal 4.7.0 out. So, the "crazy request" goes like this: 1. Can we stop implementing irrelevant improvements? Can we stop working on our pet projects for a moment? (I'm _not_ talking about important improvements for Drupal 4.8/5.0.) 2. Can we stop discussing things you are not going to start working on the next few days? This is not the time to waste time and resources with discussions that lead no where. The focus is clear. Thanks. -- Dries Buytaert :: http://buytaert.net/

1 0

hook_install: pgsql: check version number
by Keve 09 Mar '06

09 Mar '06

Hi, I am not very familiar with Postgresql. I wrote taxonomy_access.install file, but for POSTGRESQL priot to 8.0, I need to make a BIT_OR aggregate function. Do you think this will work OK for pg? if (version_compare(pg_version(), '8.0', '<')) { // PRIOR TO POSTGRESQL 8.0: making a BIT_OR aggregate function } Many thanks, Keve.

3 5

nice read: usability tests for Wikipedia online
by Bèr Kessels 09 Mar '06

09 Mar '06

Hello, See http://www.kdedevelopers.org/node/1845 (http://openusability.org/download.php/89/germanwikipedia_usabilitytest_edit…) The biggest part is (interesting, but) very wikipedia specific. However, chapter 3.4: editing and previewing has some remarkable points: * Hide the "edit" tab when previewing. Apparently that caused a lot of confusion. * Style the preview better. 'Big bold red border" or so. Furthermore it contains a lot of good ideas for when you design/develop your specific Drupal site, tha twill be used by a larger audience. Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ] Sympal draait nu voor het grootste deel al op 4.7: http://help.sympal.nl/sympal_draait_nu_voor_het_grootste_deel_al_op_4_7

4 4

Forms.module for 4.7
by Boris Mann 09 Mar '06

09 Mar '06

See this? http://www.jotform.com/index My personal idea (i.e. handwaving) for forms.module for 4.7 is that it would provide support functions to be able to build forms on the fly. Both Survey.module and perhaps CCK (e.g. for custom built node/ add forms) would use forms.module for this functionality. Thoughts on this? Anyone feel like pooling resources/funds to get this built? -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 SKYPE borismann http://www.bryght.com

12 20

Default Theme for Drupal 4.8
by Nick Lewis 08 Mar '06

08 Mar '06

Yesterday morning, Dries informed me of the following plans for 4.8: (quote) 1. A new default theme that is more slick. We're done with Bluemarine. 2. A dashboard module to replace the current main administration page (?q=admin). 3. A reorganization of the administration pages. 4. An install system. I've been storming away at items 1,2 and 3 and didn't even know that there were already plans to put this in the next version. With this news, I'd like to offer my support to any current efforts, and to give an overview of what I've accomplished so far that could be of benefit to item one. I'd put my GPL work on the CVS, but I don't think I've been granted access yet. So, I'll just give a brief overview of where I'm at, and see who comes out of the woodwork (I know... 4.7's bugs... see bottom if you're pissed...). For now, I'll spare y'all and keep it to item one: 1.So I've been working on one theme, Curved_Slate, but a variety of factors (my stupid head, the experiemental nature, and the so far disorganized approach to version tracking have lead it to be bugtacular for the moment.) I'm currently in the process of going backwords, and modularizing it into a a lightweight configuration, which can be easily extened into the heavy weight configuration. If no work has been done thus far on the default theme for 4.8, a lightweight distro (no js, or experiemental scripts, just templates, art and CSS) might provide a good starting point. The theme is has largely solved a number of persistant drupal themeing problems -- namely: 1. all css 2. .main-content expands and contracts smoothly in response to various $layout configurations. 3. all columns grow and shrink perfectly to fit any page height 4. page.tpl.php ordered content, sidebars, footer. 5. min-max width support in both firefox and safari (albeit, by way of an ugly hack): [see: http://nicklewis.smartcampaigns.com/themes/curved_slate/default_styles/layo… ] 6.A page.tpl.php file that nevertheless looks an awful lot like good old box_grey 7. Only two wrapper divs 8. You can easily (especially with some PHP scripting) expand and contract the columns or #main div to fit whatever needs you have. The theme most likely doesn't support IE5 (IE5 -- the great ugly stick of websites...) -- but I don't really care, and my guess is it would be more to drupal's benefit to focus on the 95% of web users who use modern browsers, than to settle for tables and hacks so that grandma on the mac classic can keep up with her persistant reading of online content (though my grandma tells me she's enjoyed reading my blog -- and she uses IE 4!, so it might not be so bad... but grandmas lie sometimes....) And, we could always keep bluemarine around for her. It wouldn't be terribily difficult to setup something to detect browsers that won't support standards, and serve them a crappy-browser-safe theme. Anyways, I'd be happy to throw my efforts this direction, but don't want to step on any toes, so let me know if your working on the same thing. Otherwise, provided I can login to the CVS, I'd be happy to CVS-itize a bare bones version of my theme as a place to start. A sidenote: ---Curvy Corners, a dream that Rico's Apache Liscense prevents--- I know practically nothing about Javascript... but... this is what I've hacked together to generate curved corners. The curved corners script is now a 15 kilobyte dandy (down from Rico's 150kb library). sourcecode: http://nicklewis.smartcampaigns.com/modules/jstoolbox/rico.js However, practical considerations (such as making it dead simple to implement curved corners) have forced me to use a patched Prototype 1.5 beta library source code: http://nicklewis.smartcampaigns.com/modules/jstoolbox/prototype.js While this approach is still buggy, and their are other techniques like sliding doors (when considering how short life actually is, sliding doors looks like less and less of an ideal solution), with those two scripts included, I can generate a curved corner around any part of the site. Take a look at the code that actually creates those corners on my blog: <script type="text/javascript"> var roundCorners = Rico.Corner.round.bind(Rico.Corner); roundCorners('div#main'); roundCorners('div#top-nav', {corners:'bl br'}); roundCorners('div.downloads'); roundCorners('div#compose-options-right'); roundCorners('.sidebar div.block',{border:'#eeeeee'}); roundCorners('div#footer',{border:'#eeeeee'}); </script> I'd argue that the simplicity of the Javascript solution is beautiful (I realize that its lacking in a lot of areas that developers tend to focus on, but for mid-level users, this stuff is golden). Its not something that other CMS's offer, and I think its a subtle feature that could set drupal apart. If anyone has any insight into this it would be very appreciated. That's enough for one night (er... morning for y'all continentals). Onward, Nick Lewis http://nicklewis.smartcampaigns.com Reference: page.tpl.php <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="<?php print $language ?>" xml:lang="<?php print $language ?>"> <head> <title><?php print $head_title ?></title> <?php print $head ?> <?php print $styles ?> </head> <body> <div id="main" class="<?php print $layout; /*THIS CLASS ALLOWS SIDEBARS TO DISAPPEAR SMOOTHLY */ ?>"> <?php if ($site_name) : ?> <div id="site-name"> <h1><a href="<?php print url() ?>" title="Index Page"><?php print($site_name) ?></a></h1> </div> <?php endif;?> <div id="header"> <?php if ($site_slogan) : ?> <span id="site-slogan"> <?php print($site_slogan) ?> </span> <?php endif;?> </div> <div id="primary-menu"> <?php print $primary_links; ?> <br class="clear" /> </div> <div id="columns" class="show-all" > <div class="cols-wrapper"> <div class="float-wrapper"> <div id="content"> <div class="main-content"> <?php if ($mission) { ?> <div id="mission"> <?php print $mission ?> </div> <?php } ?> <?php print $tabs; ?> <?php /*Supress content title if page is the front page */if (!$is_front) { ?> <h1 class="content-title"><?php print $title ?></h1> <?php } ?> <?php print $help ?> <?php if ($messages) { ?> <div id="message"> <?php print $messages ?> </div> <?php } ?> <?php print $content; ?> <?php print $breadcrumb ?> </div> </div> <?php /* remove all columns if $layout variable returns as "nosidebars" (see template.php file) */ if ($layout != "nosidebars") { ?> <?php if ($sidebar_left) { ?> <div id="sidebar-left" class="sidebar"> <?php print $sidebar_left ?> </div> <?php } ?> </div> <?php if ($layout != "left") { ?> <?php if ($sidebar_right) { ?> <div id="sidebar-right" class="sidebar"> <?php print $sidebar_right ?> </div> <?php } ?> <?php } ?> <?php } ?> <div class="clear" id="em"></div> <div id="footer"> <?php print $footer_message ?> <?php print $closure ?> </div> </div> </div> </div> <?php include "$onload_js"; ?> </body> </html> For uppity folk: I'm sorry, but I am swamped with work, and don't have time (or really the programming knowledge) to take on those bugs -- however, all of my "put a roof over your head" work is directly related to these goals of 4.8 -- I figure some contribution is better than no contribution. I'm very interested in having my efforts pay off for drupal as a whole. That's my excuse and I'm sticking to it.

5 4

active record tutorial
by Adrian Rossouw 08 Mar '06

08 Mar '06

http://www-128.ibm.com/developerworks/java/library/j-cb03076/?ca=dgr- lnxw01ActiveRecord The migrations stuff shows why i believe we need to move towards using arrays to create tables. The actual active record stuff is very much possible / probably how the forms api 2.0 will end up working. (ie: define fields as part of the form, where form could be a node form for instance and you just edit and hit save/submit/execute afterwards) -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com

1 0