semanticscuttle-devel Mailing List for SemanticScuttle (Page 10)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Thanks to the work of Christian Weiske.

Benjamin HUYNH KIM BANG
http://benjamin.hkb.fr/contact.htm

Hi all,

After some heavy development in the last weeks, a new feature is
complete and waits to be tested: Voting. Every registered user can vote
for or against a bookmark. Bookmark lists can be sorted by voting.
If you are interested in this feature, do not hesitate to try it out!

To do that, install a *fresh* copy of SemanticScuttle on a *copy*  of
your database directly from SVN trunk. SVN instructions are at
http://sourceforge.net/scm/?type=svn&group_id=211356

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

All your propositions seems very good for me.

I have just one remark about the Google DOJO API. The goal is to have AJAX
tree and things like that into SScuttle. The goal was to avoid having many
AJAX script but one DOJO library. However, after using it, I don't know if
it was a gain of time or not. I admit that the interface is maybe
slower/heavier. Have you knowledge about AJAX behaviour? Have you knowledge
into other solutions like JQUERY library?

DOJO http://www.dojotoolkit.org/
JQUERY http://jquery.com/

Maybe could the 3 other points managed before this one? Have you a time
prevision?

Benjamin HUYNH KIM BANG
http://benjamin.hkb.fr/contact.htm

On Fri, Oct 2, 2009 at 4:31 PM, Christian Weiske <cw...@cw...> wrote:

> Hi Benjamin,
>
>
> Now that SemanticScuttle version 0.94 is out - thanks for releasing it
> - I'd like to talk to you about the next one.
>
> There is one big bug [1] that nearly would justify an own release.
> For that bug, I'd like to move SemanticScuttle to a directory schema
> similar to [2]. We will have a "www" directory in which all publicy
> accessible files will be located. All other php files will be in
> "src". This gives us for one greater security against calls on php
> files that are only meant to be included but not called directly. It
> would also allow us to easily provide the whole application as a PEAR
> package in the future if we want that (would give users the
> possibility to install SemanticScuttle with a single command).
>
> The second thing I would like to change in that version is the coding
> standard. You once told me that you tried to keep the previous coding
> style of Scuttle, but have no problem changing that.
> The PEAR coding standards [3] are very widely used now (even Zend
> Framework adopted them and extendet them a bit), a lot of tools provide
> support for it - so this seems to be a good choice. I'd try to convert
> the whole code (except includes of course) and add phpdocumentor-style
> function docblocks [4] to all those functions, getting them documented.
>
> Item #3 on my list is bug #2862722: Option to disable Google AJAX API
> [5]
> Benjamon, could you explain where we use the google javascript apis -
> and if we actually need them? I did not look very deep at that code yet.
>
> The last item is bug #2830234: LDAP authentication [6].
> At work I wrote a patch for it, utilizing the nifty PEAR Auth [7]
> package. PEAR packages generally are not bundled but installed
> separately either via the Linux distribution's package manager or the
> pear command line installer itself. Since SemanticScuttle will
> still work without it, I suggest we do not bundle Auth and tell people
> what to do when they need LDAP/IMAP/SOAP/Kerberos/SAP/...
> authentication. What do you think?
>
>
> Because that version contains so many changes, I'd call it version
> 0.10.0.
>
>
> [1]
>
> http://sourceforge.net/tracker/?func=detail&aid=2863677&group_id=211356&atid=1017430
> [2] http://wiki.php.net/pear/rfc/pear2_standards#directory_structure
> [3] http://pear.php.net/manual/en/standards.php
> [4]
>
> http://manual.phpdoc.org/HTMLSmartyConverter/HandS/phpDocumentor/tutorial_tags.pkg.html
> [5]
>
> http://sourceforge.net/tracker/?func=detail&aid=2862722&group_id=211356&atid=1017432
> [6]
>
> http://sourceforge.net/tracker/?func=detail&aid=2830234&group_id=211356&atid=1017433
> [7] http://pear.php.net/package/Auth
>
> Regards,
> Christian Weiske
>

Hi Benjamin,

> I have just one remark about the Google DOJO API. The goal is to have
> AJAX tree and things like that into SScuttle. The goal was to avoid
> having many AJAX script but one DOJO library. However, after using
> it, I don't know if it was a gain of time or not. I admit that the
> interface is maybe slower/heavier. Have you knowledge about AJAX
> behaviour? Have you knowledge into other solutions like JQUERY
> library?
> 
> DOJO http://www.dojotoolkit.org/
> JQUERY http://jquery.com/
> 
> Maybe could the 3 other points managed before this one? Have you a
> time prevision?

At work we often work with jquery, so I have some experience with it.
Of course we can put the ajax lib problem aside and do the other things
first. That's probably the best way.

About the time - I have no idea. I'll try to do it as fast as possible
before losing interest :) This weekend is DevHouse in Berlin; I'll
probably have some time to hack on it there.

Christian

Hi Benjamin,

Now that SemanticScuttle version 0.94 is out - thanks for releasing it
- I'd like to talk to you about the next one.

There is one big bug [1] that nearly would justify an own release.
For that bug, I'd like to move SemanticScuttle to a directory schema
similar to [2]. We will have a "www" directory in which all publicy
accessible files will be located. All other php files will be in
"src". This gives us for one greater security against calls on php
files that are only meant to be included but not called directly. It
would also allow us to easily provide the whole application as a PEAR
package in the future if we want that (would give users the
possibility to install SemanticScuttle with a single command).

The second thing I would like to change in that version is the coding
standard. You once told me that you tried to keep the previous coding
style of Scuttle, but have no problem changing that.
The PEAR coding standards [3] are very widely used now (even Zend
Framework adopted them and extendet them a bit), a lot of tools provide
support for it - so this seems to be a good choice. I'd try to convert
the whole code (except includes of course) and add phpdocumentor-style
function docblocks [4] to all those functions, getting them documented.

Item #3 on my list is bug #2862722: Option to disable Google AJAX API
[5]
Benjamon, could you explain where we use the google javascript apis -
and if we actually need them? I did not look very deep at that code yet.

The last item is bug #2830234: LDAP authentication [6].
At work I wrote a patch for it, utilizing the nifty PEAR Auth [7]
package. PEAR packages generally are not bundled but installed
separately either via the Linux distribution's package manager or the
pear command line installer itself. Since SemanticScuttle will
still work without it, I suggest we do not bundle Auth and tell people
what to do when they need LDAP/IMAP/SOAP/Kerberos/SAP/...
authentication. What do you think?

Because that version contains so many changes, I'd call it version
0.10.0.

[1]
http://sourceforge.net/tracker/?func=detail&aid=2863677&group_id=211356&atid=1017430
[2] http://wiki.php.net/pear/rfc/pear2_standards#directory_structure
[3] http://pear.php.net/manual/en/standards.php
[4]
http://manual.phpdoc.org/HTMLSmartyConverter/HandS/phpDocumentor/tutorial_tags.pkg.html
[5]
http://sourceforge.net/tracker/?func=detail&aid=2862722&group_id=211356&atid=1017432
[6]
http://sourceforge.net/tracker/?func=detail&aid=2830234&group_id=211356&atid=1017433
[7] http://pear.php.net/package/Auth

Regards,
Christian Weiske

Hi all,

Benjamin just released version 0.94 of SemanticScuttle, full of bug
fixes!

Announcement:
http://sourceforge.net/news/?group_id=211356

Changelog:
http://semanticscuttle.svn.sourceforge.net/viewvc/semanticscuttle/trunk/ChangeLog?revision=383&view=markup

Regards,
Christian Weiske

Hi Benjamin,

I think enough changes have been committed to release a new version.
All changes are noted now in the ChangeLog file. I had a friend testing
SemanticScuttle with me, so it should be safe to release it.

I have to say that I did not touch the unit tests at all, and that I
did not rely on them. What I did was only fixing bugs, making the HTML
valid and code working. I answered many of the currently open forum
threads and closed them.
There is only one new feature; cookie detection. I refrained the LDAP
authentication patch for a new feature-only version because I think
it's necessary to get the bugfix release out.

Apart from the things I mentioned, the configuration system changed a
bit. Current configuration files still work as they always did, but for
new installations, things are easier now. The default configuration
file (config.inc.php.dist) contains only 11 configuration options - to
make it as easy as possible for new users. All other config options are
in config.default.inc.php now, because they are often not changed
anyway. Configuration values are explained in detail in those files
now, too.

Would you like to test the changes? You are the only one who is able to
deploy new file releases, so it's your turn now.

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

Hi there,

Is there any development or activity going on in semantic scuttle?

I would like to implement external authentication - i.e. authenticating
users against LDAP or a different SQL database.
There are several authentication abstraction layers available, for
example PEAR's Auth [1] or Zend Auth [2]. It would allow us to support a
dozen of authentication methods with minimal effort.

Since Zend is distributed as one single package, the dependencies are
very large - I'd prefer PEAR's Authentication package. Developing it
all ourselves would be possible, but is a large effort.

What do you think?

[1] http://pear.php.net/package/Auth
[2] http://framework.zend.com/manual/en/zend.auth.html

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

Hello,

While fixing some notices and warnings, I saw that the code style does
not follow common rules. Sometimes tabs are used to indent, sometimes
spaces.

What is the preferred coding style in SemanticScuttle?

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

 Nombreuses seront les options de l'admin quand il sera
terminé (changement de design, validation des utilisateurs,
etc...) la question, est donc de savoir si les options seront
conservées dans un fichier texte, ou dans la base de
donnée.  

 Si l'on utilise la base de donnée reste à savoir
quelles options restent dans le fichiers de config.  
 Lilobase  

2008	Jan	Feb	Mar	Apr	May	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec
2009	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (2)	Sep (1)	Oct (5)	Nov (4)	Dec (2)
2010	Jan (9)	Feb (4)	Mar (1)	Apr	May	Jun (2)	Jul (1)	Aug (1)	Sep (6)	Oct	Nov	Dec
2011	Jan (20)	Feb (47)	Mar (25)	Apr (19)	May (58)	Jun (14)	Jul (5)	Aug (4)	Sep	Oct	Nov	Dec
2012	Jan (1)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2013	Jan	Feb	Mar (1)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2014	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (1)	Dec
2015	Jan	Feb	Mar	Apr	May	Jun	Jul (2)	Aug	Sep	Oct	Nov	Dec

semanticscuttle-devel Mailing List for SemanticScuttle (Page 10)

semanticscuttle-devel — General discussion about SemanticScuttle development