wxcode-users

[wxCode-users] Next issue

[sdfkjsjlh s. <sdf...@ya...>]

 Hi Francesco,

Here's my next question. The mmwx web site and logo haven't updated although they've been online for nearly a week. The docs say they should be updated from the SVN repo but it's not happening. Can you investigate, please?

Also, /home/groups/w/wx/wxcode/htdocs/components/mmwx/ contains the old src and CVS directories. They seem to be fairly standard but, since I've changed to SVN, can I get rid of those now?
Should the SVNrepo. be visible instead?

Any update on the bugs I reported? It looks like the screenshot problem is caused by SF turning off directory listing by default. you can turn it back on manually but some other method of display
would have to be better. 

Thanks,

 Gary.


      

Re: [wxCode-users] Next issue

[Francesco <f18...@ya...>]

Hi,

2010/5/11 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>:
> Here's my next question. The mmwx web site and logo haven't updated although
> they've been online for nearly a week. The docs say they should be updated
> from the SVN repo but it's not happening. Can you investigate, please?
I'm sorry but SF disabled cron tasks some time ago and so I need to
manually run the update script to get things updated.
However I've noticed that you placed some stuff in the components/mmwx
folder of the wxCode website without adjusting the privileges of the
"group" and so I cannot remove them (with a simple procedure)... could
you please remove all the stuff from
/home/groups/w/wx/wxcode/htdocs/components/mmwx so that I can check
out inside it the new mmwx website? TIA.

> Also, /home/groups/w/wx/wxcode/htdocs/components/mmwx/ contains the old src
> and CVS directories. They seem to be fairly standard but, since I've changed
> to SVN, can I get rid of those now?
> Should the SVN repo. be visible instead?
yes, it should. I'll fix it asap.

> Any update on the bugs I reported? It looks like the screenshot problem is
> caused by SF turning off directory listing by default.
I should have fixed this by adding that .htaccess file as I mentioned
in the other mail... do you still see the SF message when clicking on
"screenshots"?

>you can turn it back
> on manually but some other method of display
> would have to be better.
yes, other display methods would be better and I'd gladly accept
patches for that (an easy solution which comes to my mind is to place
a "index.php" file inside all subfolders of the screenshots folder --
and make that index.php nicely format the .png and .jpeg files present
in that same folder) :)

Francesco

Re: [wxCode-users] Next issue

[sdfkjsjlh s. <sdf...@ya...>]

 Hi Francesco,




________________________________
From: Francesco <f18...@ya...>
To: wxc...@li...
Sent: Wed, May 12, 2010 7:46:29 AM
Subject: Re: [wxCode-users] Next issue

Hi,

2010/5/11 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>:
> Here's my next question. The mmwx web site and logo haven't updated although
> they've been online for nearly a week. The docs say they should be updated
> from the SVN repo but it's not happening. Can you investigate, please?
I'm sorry but SF disabled cron tasks some time ago and so I need to
manually run the update script to get things updated.

That's a nuisance. Having to rely on you before I can see updates isn't going to work for either of us. How about a method
where each user can update their own code? That would save you the obvious pain and give us immediate updates. ;-)

However I've noticed that you placed some stuff in the components/mmwx
folder of the wxCode website without adjusting the privileges of the
"group" and so I cannot remove them (with a simple procedure)... could
you please remove all the stuff from
/home/groups/w/wx/wxcode/htdocs/components/mmwx so that I can check
out inside it the new mmwx website? TIA.

OK, sure. I've removed the web site. I noticed that you got rid of the CVS yesterday. Thanks.


> Also, /home/groups/w/wx/wxcode/htdocs/components/mmwx/ contains the old src
> and CVS directories. They seem to be fairly standard but, since I've changed
> to SVN, can I get rid of those now?
> Should the SVN repo. be visible instead?
yes, it should. I'll fix it asap.


OK, thanks.

> Any update on the bugs I reported? It looks like the screenshot problem is
> caused by SF turning off directory listing by default.
I should have fixed this by adding that .htaccess file as I mentioned
in the other mail... do you still see the SF message when clicking on
"screenshots"?

No, I get the directory listing now. I noticed that yesterday, too.

>you can turn it back
> on manually but some other method of display
> would have to be better.
yes, other display methods would be better and I'd gladly accept
patches for that (an easy solution which comes to my mind is to place
a "index.php" file inside all subfolders of the screenshots folder --
and make that index.php nicely format the .png and .jpeg files present
in that same folder) :)

OK, I'll see what I can come up with.

Thanks for the changes.

Gary.


      

Re: [wxCode-users] Next issue

[Francesco <f18...@ya...>]

Hi,


2010/5/12 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>:
> 2010/5/11 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>:
>> Here's my next question. The mmwx web site and logo haven't updated
>> although
>> they've been online for nearly a week. The docs say they should be updated
>> from the SVN repo but it's not happening. Can you investigate, please?
> I'm sorry but SF disabled cron tasks some time ago and so I need to
> manually run the update script to get things updated.
>
> That's a nuisance. Having to rely on you before I can see updates isn't
> going to work for either of us. How about a method
> where each user can update their own code? That would save you the obvious
> pain and give us immediate updates. ;-)
well, I've now fixed the setup of the mmwx website so that if you want
to see immediate updates of mmwx website you don't need to rely on me
anymore:
1) commit changes to mmwx's SVN repo
2) log into wxcode/htdocs/components/mmwx (I use Putty from Windows)
3) run "svn update"
;)

>>you can turn it back
>> on manually but some other method of display
>> would have to be better.
> yes, other display methods would be better and I'd gladly accept
> patches for that (an easy solution which comes to my mind is to place
> a "index.php" file inside all subfolders of the screenshots folder --
> and make that index.php nicely format the .png and .jpeg files present
> in that same folder) :)
>
> OK, I'll see what I can come up with.
>
> Thanks for the changes.
no problem!

Francesco

Re: [wxCode-users] Next issue

[sdfkjsjlh s. <sdf...@ya...>]

________________________________
From: Francesco <f18...@ya...>
To: wxc...@li...
Sent: Wed, May 12, 2010 2:13:15 PM
Subject: Re: [wxCode-users] Next issue

Hi,


well, I've now fixed the setup of the mmwx website so that if you want
to see immediate updates of mmwx website you don't need to rely on me
anymore:
1) commit changes to mmwx's SVN repo
2) log into wxcode/htdocs/components/mmwx (I use Putty from Windows)
3) run "svn update"
;)

That's great, many thanks.

>>you can turn it back
>> on manually but some other method of display
>> would have to be better.
> yes, other display methods would be better and I'd gladly accept
> patches for that (an easy solution which comes to my mind is to place
> a "index.php" file inside all subfolders of the screenshots folder --
> and make that index.php nicely format the .png and .jpeg files present
> in that same folder) :)
>
> OK, I'll see what I can come up with.

I've created a solution for this. You can see it in action If you click on the mmwx screenshots link.

You'll notice there's a new index.php in mmwx's screenshots directory. It uses the existing facilities to create a wxCode page and displays any png and jpg images
found in the directory. If one image is found, it will create one img tag to display the image. If more than one is found, it creates a Slimbox2 link block so you get
the nice display. I couldn't see the point in forcing the user to click on the image to view the same image in Slimbox, if there was just the one, so that's why that
case gets the single img tag.

I borrowed some images from keybinder to make the demo more interesting.

To make it site wide, we just need to move the js and css to a global location and adjust the links. Users will need to enter their component's name into the code
as they do for the website, unless there's a way to automate that, which would be preferable. Actually, we could just adjust the link to send it via GET or pull it out
of the session.

I'd like to adjust the writeScreenshotLink() function to use Slimbox, too, if you approve, but we should get this one in place and working so that it suits you first.

My only question now is why the website link is still inactive. ;-)
Did you have any thoughts as to why the build script is still failing?

Cheers,

  Gary.


      

Re: [wxCode-users] Next issue

[sdfkjsjlh s. <sdf...@ya...>]

 Hi,

writeSnippet() is working again now, too. :-)

Thanks.


      

Re: [wxCode-users] Next issue

[sdfkjsjlh s. <sdf...@ya...>]

 Just for the hell of it the second screenshot on mmwx's website demonstrates the Slimbox version of writeScreenshotLink(). ;-)

Ciao.


      

Re: [wxCode-users] Next issue

[Francesco <f18...@ya...>]

Hi,
   sorry again for the delay with this reply...

2010/5/13 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>:
>  Just for the hell of it the second screenshot on mmwx's website
> demonstrates the Slimbox version of writeScreenshotLink(). ;-)
very nice!

I see that there's currently a big comment block on
screenshots/mmwx/index.php... I think it would be nice to put the
"js", the "css" and the index.php file (without that commented block)
in the other subfolders of wxcode/htdocs/screenshots... is it ok for
you?

Even better, instead of duplicating the "js" and "css" folders for
every component with screenshots, it would probably be better to put a
single copy into "screenshots" folder and then use ../js/slimbox2.js
and ../css/slimbox2.css to reference to them...

Thanks,
Francesco

Re: [wxCode-users] Next issue

[sdfkjsjlh s. <sdf...@ya...>]

 Hi,


I see that there's currently a big comment block on
screenshots/mmwx/index.php... I think it would be nice to put the
"js", the "css" and the index.php file (without that commented block)
------------

You can't be talking about the function documentation, can you? Else you've lost me.


in the other subfolders of wxcode/htdocs/screenshots... is it ok for
you?
-----
Absolutely not! :-)

Even better, instead of duplicating the "js" and "css" folders for
every component with screenshots, it would probably be better to put a
single copy into "screenshots" folder and then use ../js/slimbox2.js
and ../css/slimbox2.css to reference to them...
--------------

Of course it was never my intention to duplicate those. I thought that was obvious. :-O
IIRC I mentioned that the Slimbox files need to go somewhere global, index.php into each screenshot dir. and have the name of the project inserted into it, unless we pull that from elsewhere, which would be much better as it would remove the need for users to do it.

I really dislike having the site code dumped into a directory which is user-accessible and have it mingled with directories they need to access, (cringe) however if that's your preference to stay consistent I can live with it. It's your baby. ;-)

Perhaps a better solution would be to change the code the generates the screenshot link to add the project name into the query string. That way we can put index.php into screenshots/<project> and have it work automagically. Likewise for the web site link. That way users no longer have to edit the $compname variable.

Cheers,

  Gary.


      

Re: [wxCode-users] Next issue

[sdfkjsjlh s. <sdf...@ya...>]

________________________________
I see that there's currently a big comment block on
screenshots/mmwx/index.php... I think it would be nice to put the
"js", the "css" and the index.php file (without that commented block)
in the other subfolders of wxcode/htdocs/screenshots... is it ok for
you?
-----

My apologies, I found what you were referring to and removed it.


Even better, instead of duplicating the "js" and "css" folders for
every component with screenshots, it would probably be better to put a
single copy into "screenshots" folder and then use ../js/slimbox2.js
and ../css/slimbox2.css to reference to them...
-----------

I took the liberty of moving the header lines to header.inc. I've also added the new writeScreenshotLink() to compwebsite.inc but I haven't enabled it as I didn't want to change the web site's functionality without your knowledge. I put it immediately under the existing version and you just need to rename it when you're ready. I've tested everything against the mmwx site, including the temporarily renamed new version of writeScreenshotLink(), and haven't seen any problems. The original files are backed up as <filename>.bak.
I moved Slimbox's css and js folders to the site root. That way we only need the one copy for both purposes.

I'm happy to go through and put the screenshot index into the other directories, if you'd like.

Users still need to set $compname in index.php. We can remove that requirement but it will require changing some code. I played around with that for a while and can see most of what needs to be done but it gets hard to debug and see what's going on when you don't have the whole site and it's DB to work with. Basically, you'd need to change queryres_table() in dboutput.inc to add the query string "?name=$comp[name]" to $compurl['website'] and $compurl['screenshots']. We could then adjust the index.php files to use the name passed. Doing that for $compurl['website'] causes problems for file checking in write_helper_link(), though, so it needs a bit more investigation.

Enjoy.


      

Re: [wxCode-users] Next issue

[Francesco <f18...@ya...>]

Hi Gary,


2010/5/19 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>:
> I took the liberty of moving the header lines to header.inc. I've also added
> the new writeScreenshotLink() to compwebsite.inc but I haven't enabled it as
> I didn't want to change the web site's functionality without your knowledge.
I've tested and enabled it; it works just fine, thanks.
Btw if you want to suggest changes to wxCode website you're encouraged
to created patches and post them on this mailing list rather than
directly modifying the files on the webserver.

> I put it immediately under the existing version and you just need to rename
> it when you're ready. I've tested everything against the mmwx site,
> including the temporarily renamed new version of writeScreenshotLink(), and
> haven't seen any problems. The original files are backed up as
> <filename>.bak.
> I moved Slimbox's css and js folders to the site root. That way we only need
> the one copy for both purposes.
I think it's better to place both .css and .js files in the root
folder as other .css and .js files are placed there so I've moved
slimbox files out of css and js folders. I also moved the gifs in the
"images" folder, which I think is more appropriate.
Could you please remove the "js" and "css" folders since they have no
group write permission? Please remember to always adjust permissions
(adding the group-write bit) of folders/files you place in
"screenshots" folder or anywhere else in the wxCode website.

> I'm happy to go through and put the screenshot index into the other
> directories, if you'd like.
I think this should be done by other maintainers, if they're interested...

> Users still need to set $compname in index.php. We can remove that
> requirement but it will require changing some code. I played around with
> that for a while and can see most of what needs to be done but it gets hard
> to debug and see what's going on when you don't have the whole site and it's
> DB to work with. Basically, you'd need to change queryres_table() in
> dboutput.inc to add the query string "?name=$comp[name]" to
> $compurl['website'] and $compurl['screenshots']. We could then adjust the
> index.php files to use the name passed. Doing that for $compurl['website']
> causes problems for file checking in write_helper_link(), though, so it
> needs a bit more investigation.
I think it's really easy for any maintainer to setup his
lightbox-enabled screenshots page if he wants to, so I'd avoid
modifying the existing code just to avoid users to modify the PHP file
they put in their screenshots folder..
Forcing maintainers to open that index.php also makes them more aware
of the possibilities they have and aware of how the website work ;)

Thanks!
Francesco

Re: [wxCode-users] Next issue

[sdfkjsjlh s. <sdf...@ya...>]

________________________________
From: Francesco <f18...@ya...>
To: wxc...@li...
Sent: Sun, May 23, 2010 1:53:38 PM
Subject: Re: [wxCode-users] Next issue

Hi Gary,


2010/5/19 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>:
> I took the liberty of moving the header lines to header.inc. I've also added
> the new writeScreenshotLink() to compwebsite.inc but I haven't enabled it as
> I didn't want to change the web site's functionality without your knowledge.
I've tested and enabled it; it works just fine, thanks.
--------

Cool. :-)


Btw if you want to suggest changes to wxCode website you're encouraged
to created patches and post them on this mailing list rather than
directly modifying the files on the webserver.
------------

Yeah, I know. I wouldn't do that ordinarily. I see you've added the website to SVN so that should solve the problem.

> I moved Slimbox's css and js folders to the site root. That way we only need
> the one copy for both purposes.
I think it's better to place both .css and .js files in the root
folder as other .css and .js files are placed there so I've moved
slimbox files out of css and js folders. I also moved the gifs in the
"images" folder, which I think is more appropriate.
Could you please remove the "js" and "css" folders since they have no
group write permission? Please remember to always adjust permissions
(adding the group-write bit) of folders/files you place in
"screenshots" folder or anywhere else in the wxCode website.
------------

OK, if that's your desire. 
Done.


> I'm happy to go through and put the screenshot index into the other
> directories, if you'd like.
I think this should be done by other maintainers, if they're interested...


Sure, no problem. I only offered because I thought you mentioned it earlier.

Cheers,

  Gary.