Menu
▾
▴
opendocumentphp-developers — OpenDocumentPHP-Developers
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
(21) |
Apr
(5) |
May
(10) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
|
Feb
(14) |
Mar
(2) |
Apr
|
May
(4) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Norman M. <no...@se...> - 2006-03-29 14:54:32
|
Hi! After some very hard bug fixing today, I put a new release on sf.net. POC 0.4.5 is its name. The main difference between POC 0.4.4 and 0.4.5 is, that the new one should produce correct OpenDocumentPackege outputs. The code in the sample directory should work on linux and windows servers. Please check it asap. Yours, Norman |
|
From: Norman M. <no...@se...> - 2006-03-29 09:05:05
|
Hi folks, As we are heading the POC 0.5.0, I have put some more informations on = the website. You will find the API under http://opendocumentphp.sf.net/poc/docs/0.5.0/index.html, the test suite informations under = http://opendocumentphp.sf.net/poc/tests/0.5.0/index.html and a code coverage report under http://opendocumentphp.sf.net/poc/coverage/0.5.0/index.html. Also I did some tiny changes to the source code structure, as you can = see in SVN. Regards, Norman |
|
From: Norman M. <no...@se...> - 2006-03-23 10:41:33
|
Hi Flavio! That part is still missing. Alex wanted to develop such things. If you take a look at the code in TestOuput.php, i think the method is called "makeContent" or "makeBody", you can see how you can add paragraphs and headings. If you need some other things, simply ask for them or ... make your own contribution to our development. I run a little bit out of time this week, so please expect any further development of the code not before end of next week. Yours, Norman |
|
From: Flavio R. <fla...@gm...> - 2006-03-23 10:07:28
|
Hi Norman your new file works on my system, thank you! I notice both title and author tags get set correctly, but I do not see any of my content of the <textarea> -tag in TestInput.php transmitted to test.odt? Instead I see the following to lines: The first step This is a little test! Any idea what went wrong here? -Flavio Norman Markgraf wrote: > Hi Flavio, > > Thank you for testing OpenDocumentPHP. The problems you have encountered > with TestOutput.php have mainly two reasons. The first is that in the > distribution is an old version of TestOutput.php (and TestInput.php). Please > try > it with the current SVN release or contact me via private mail, and I will > send you the current files as an email. > > The second one is a really bad one. Our current solution to use the > "int_set..." statement in TestOutput.php has shown up to be a bad choice. I > have tried to fix this with a very ugly hack. I hope this will help you: > > Replace the old "ini_set" statement with: > > // Very dirty hack ... > $dsep = DIRECTORY_SEPARATOR; > $IP = dirname( realpath( dirname( dirname ( __FILE__) . "$dsep..$dsep") ) ); > $sep = (DIRECTORY_SEPARATOR == "\\") ? ";" : ":"; > ini_set( "include_path", ini_get( "include_path" ). "$sep$IP" ); > // > > And remove ALL with an addNo... Call in TestOutput.php. This will fix most > of the errors, I hope! > > Yours > > Norman > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > _______________________________________________ > OpenDocumentPHP-Developers mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opendocumentphp-developers > > |
|
From: Norman M. <no...@se...> - 2006-03-23 09:05:30
|
Hi Flavio, Thank you for testing OpenDocumentPHP. The problems you have encountered with TestOutput.php have mainly two reasons. The first is that in the distribution is an old version of TestOutput.php (and TestInput.php). = Please try=20 it with the current SVN release or contact me via private mail, and I = will send you the current files as an email. The second one is a really bad one. Our current solution to use the "int_set..." statement in TestOutput.php has shown up to be a bad = choice. I have tried to fix this with a very ugly hack. I hope this will help you: Replace the old "ini_set" statement with: // Very dirty hack ...=20 $dsep =3D DIRECTORY_SEPARATOR; $IP =3D dirname( realpath( dirname( dirname ( __FILE__) . = "$dsep..$dsep") ) ); $sep =3D (DIRECTORY_SEPARATOR =3D=3D "\\") ? ";" : ":"; ini_set( "include_path", ini_get( "include_path" ). "$sep$IP" ); // And remove ALL with an addNo... Call in TestOutput.php. This will fix = most of the errors, I hope! Yours Norman |
|
From: Flavio R. <fla...@gm...> - 2006-03-22 20:12:05
|
noticed I could fix the error on line 75 just with changing some letters to lower case. but then I get following error in my test.odt Fatal error: Call to undefined method Content::addNoScript() in /var/www/hediger/opendocument/opendoc-sf1/samples/TestOutput.php on line 58 -Flavio |
|
From: Flavio R. <fla...@gm...> - 2006-03-22 19:56:26
|
Noticed I also have to add the exact path to my opendocument-src directory to the ini_set function, because for some reason the recursive ..\ does not work on my system. I guess this is also os-specific. Proceeding: When I execute TestOutput.php, I get an .odt file, but with the following content: Fatal error: Call to a member function addFontFace() on a non-object in mypath/opendoc-sf1/samples/TestOutput.php on line 75 what is that? -Flavio |
|
From: Flavio R. <fla...@gm...> - 2006-03-22 19:44:22
|
Hi Noticed following does not work under linux: in samples/TestOutput.php: line 17: ini_set( "include_path", ini_get( "include_path" ). ";..\\;.\\styles\\;..\\styles\\;.\\content\\;..\\content\\" ); the function does execute, but the result is not what we are looking for: for linux the following works: -notice the change of the delimiter from ";" to ":". ini_set( "include_path", ini_get( "include_path" ). ":..\\:.\\styles\\:..\\styles\\:.\\content\\:..\\content\\" ); I posted this as a bug @ the sf-site of this project. Please reply if you fix this. Also, there is a variable called $PathToDocument which is set with a Windows-like content: "D:/PHP/OpenDocument". While I haven't found how this affects the process, I guess it would not have the desired effect on unix/linux systems. -Flavio |
|
From: Norman M. <no...@se...> - 2006-03-20 14:44:49
|
Dear Developers, I released POC 0.4.4 some minutes ago. This is the first public release of what we will call "proof of concept"-code (aka POC) of OpenDocumenPHP. Please check it out at sourceforge.net. It has all the code in /poc/src tree. You can simply copy everything under /poc/src to your htdocs/ dir in your web server and run samples/TestInput.php for a little test drive. BE AWARE! YOU NEED AT LEAST PHP 5.1.1!!! Or, if you have the latest Phing installed from there SVN, you can type "phing test" for a PHPUnit2 unit test. If you try "phing production", you will get a distribution without unit tests unter /poc/production. It is better to try this in your web server. I hope the work by Alex and my, will be useful for you all. DocWriters: Please start writing! - Therefor please ask questions on this mailinglist! WebDesigner: Please start writing! Regards, Norman |
|
From: Norman M. <no...@se...> - 2006-03-13 14:01:42
|
Hi folks, We are heading to POC 0.5. By the end of this day the current SVN will = have the 0.4.3 code in it. Lots of stuff has changed since 0.3. It would be = nice, if all team members would check out the 0.4.3, because 0.5 will look = very similar to 0.4.3. We only add PHPDoc comments to 0.4.3 so we can say = that 0.5 will be the first release on sf.net. I was thinking about this Friday as a good release day for POC 0.5! Please don't commit new features to 0.4.X stables and documentation is = our task till end of the week. Thanks in advance Norman |
|
From: Norman M. <no...@se...> - 2006-03-09 10:42:04
|
Hi folks! If you want to know, what is going on in the development process and the OpenDocumentPHP-Repository mailing list is to heavy for you, you can keep up-to-date with all the commits to the svn repository with this link http://cia.navi.cx/stats/project/opendocumentphp. Regards, Norman |
|
From: Norman M. <no...@se...> - 2006-03-09 08:38:34
|
Hi folks, First let me thank you Alex, for this wonderful commit. I think the = Problem with "Log_null" is, that the real path is "Log/null.php" and their for I added a little "strtr($class_name, '_', '/')" to solve the problems with = the subdirectories. Please to all committers:=20 1) Add=20 svn:keywords=3D"Date Revision Author HeadURL Id" to your php class files commits and/or php class file base. CVS had = those things automatically added.=20 But SVN needs the permission to do so. With TrotoiseSVN you can simply click properties for each file or a subdirectory, then press Subvision choose svn:keywords as a new property = and "Date Revision Author HeadURL Id" as value. Press "Set" and we all be = fine. 2) If you change something in the tree, don't forget to add your self to = the author list by adding=20 @author Your Name <yo...@em...dress> in the main comment part (a.k.a main PHPDocument-comment) Regards Norman |
|
From: Alex L. <ad...@ya...> - 2006-03-08 23:31:48
|
Howdy guys,
Ive just committed changes to the SVN repository that changes all the
extensions on the PHP files from .php5 and .php3 to .php. Although this
may seem like a drastic step to make, as you lose all logging for the
files previously (the old files are still on the SVN logs btw..), it was
necessary to do this to get the __autoload() function working correctly.
This function is inbuilt to PHP5.x and helps you include class files
that you have referenced automatically, thus cutting down on code. The
function basically is called every time a class is loaded, this then use
the classes name to search for a .php file of the same name.
function __autoload($class_name) {
if($class_name != 'Log_null')
{
require_once("$class_name.php");
}
}
There is the code. From there I'm sure you can see why I needed to have
a unified extension throughout the package. The function is located with
the OpenDocumentFactory.php file and will stay there as its the
top-level object at present.
Well, I hope to explains it to everyone. Alex.
PS. If anyone knows where the class Log_null is being called from it
would be nice to fix it, because without the if() statement it produces
a nice Fatal Error because it cant find the file.
|
|
From: Norman M. <no...@se...> - 2006-03-08 21:50:57
|
Hi folks, While I am working on POC 0.5 and rethinking some things for stage 1, I would like to know your opinion on the following: * I guess a new structure for the source files would be a great idea, something like this: OpenDocument.php5 OpenDocumentPHP/Factory.php5 OpenDocumentPHP/FactoryTest.php5 OpenDocumentPHP/Content.php5 OpenDocumentPHP/ContentTest.php5 OpenDocumentPHP/Content/Body.php5 OpenDocumentPHP/Content/BodyTest.php5 OpenDocumentPHP/Content/Body/Text.php5 OpenDocumentPHP/Content/Body/TextTest.php5 OpenDocumentPHP/Content/Body/Drawings.php5 OpenDocumentPHP/Content/Body/DrawingsTest.php5 OpenDocumentPHP/Meta.php5 OpenDocumentPHP/MetaTest.php5 OpenDocumentPHP/Manifest.php5 OpenDocumentPHP/ManifestTest.php5 OpenDocumentPHP/SingleDocument.php5 OpenDocumentPHP/SingleDocumentTest.php5 OpenDocumentPHP/PackageDocument.php5 OpenDocumentPHP/PackageDocumentTest.php5 OpenDocumentPHP/PackageDocument/ZipFile.php4 * PHing should sort out all *Test.php5 and make a clean "Public Distribution" of OpenDocumentPHP without the test cases and maybe without the "$this->logger->debug(...)" lines. This will speed up the production code, I think. Thanks in advance Norman PS: May be you get this twice, please report if or if not? |
|
From: Alex L. <ad...@ya...> - 2006-03-08 21:06:45
|
Right, I was asked by Norman to produce some documentation on how to get the current SVN copy to work correctly, this I have done. Basically it runs over exactly what packages you need and how to install them. The PDF version can be found here : http://opendocumentphp.sourceforge.net/documents/Installing-PEAR.pdf The ODT version can be found here : http://opendocumentphp.sourceforge.net/documents/Installing-PEAR.odt Anyway, I hope that gets you guys all setup. And if you have any problems, the IRC Channel and this email address are open for you to contact. Good Luck, Alex. <http://opendocumentphp.sourceforge.net/members/yawnster.html> |
|
From: Norman M. <no...@se...> - 2006-03-08 10:51:22
|
Hi folks, While I am working on POC 0.5 and rethinking some things for stage 1, I would like to know your opinion on the following: * I guess a new structure for the source files would be a great idea, something like this: OpenDocument.php5 OpenDocumentPHP/Factory.php5 OpenDocumentPHP/FactoryTest.php5 OpenDocumentPHP/Content.php5 OpenDocumentPHP/ContentTest.php5 OpenDocumentPHP/Content/Body.php5 OpenDocumentPHP/Content/BodyTest.php5 OpenDocumentPHP/Content/Body/Text.php5 OpenDocumentPHP/Content/Body/TextTest.php5 OpenDocumentPHP/Content/Body/Drawings.php5 OpenDocumentPHP/Content/Body/DrawingsTest.php5 OpenDocumentPHP/Meta.php5 OpenDocumentPHP/MetaTest.php5 OpenDocumentPHP/Manifest.php5 OpenDocumentPHP/ManifestTest.php5 OpenDocumentPHP/SingleDocument.php5 OpenDocumentPHP/SingleDocumentTest.php5 OpenDocumentPHP/PackageDocument.php5 OpenDocumentPHP/PackageDocumentTest.php5 OpenDocumentPHP/PackageDocument/ZipFile.php4 * PHing should sort out all *Test.php5 and make a clean "Public Distribution" of OpenDocumentPHP without the test cases and maybe without the "$this->logger->debug(...)" lines. This will speed up the production code, I think. Thanks in advance Norman |
|
From: Norman M. <no...@se...> - 2006-03-08 10:01:45
|
This is a Test! |
|
From: <no...@se...> - 2006-03-08 09:43:40
|
Sorry, But could every body reading this just post a little comment, so we can check what is going wrong here? Thanks Norman |
|
From: Alex L. <ad...@ya...> - 2006-03-07 15:09:40
|
Howdy Guys, I'm just announcing that we have an IRC channel open on the Freenode network at #OpenDocumentPHP its not ours just yet as it will take a little while to get your little group registered, but me and Norman have been on there for a little while and its working perfectly. to connect direct use.. irc://irc.freenode.net/opendocumentphp Hope to chat to you guys soon. Alex |
|
From: Alex L. <ad...@ya...> - 2006-03-05 18:27:39
|
Well, I thought that I would introduce myself, test out the mailing list as I've never actually used it before. The names Alex Latchford aka Yawnster, I'm 17, currently living in London and studying Computing at Richmond College. I have a fair bit of experience with PHP, Javascript and a few other languages that I will leave out. Anyway, just a short introduction as I'm sure that we will be speaking to each other a lot more as the project progresses. Alex |
|
From: Norman M. <no...@se...> - 2006-03-05 15:38:18
|
Hi folks, I will start this mailing list with a short message on what is the = current status in the OpenDocumentPHP development. The whole text can be found = as a PDF on our project homepage (http://opendocumentphp.sourceforge.net). = This is just a not so long version of the text with less formatting and no = links. =20 Thanks to you all, Norman =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D = =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D = =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D = =3D=20 __Some remarks about me, this project, poc and "stage 1"__ _Some information about me..._ Let me first introduce myself, my name is Norman Markgraf, I was born = back in 1971, I live in a town named Bochum (Germany)2 , I have got a so call "Diplom" in math with a major in computer science.=20 I started to work with computer back in 1984, where I started = programming in Basic and assembler on a Commodore C=3D64, too. I have work with several programming languages like Pascal, C, C++, Java, Haskel, PgSQL, Fortran, = . and PHP.=20 The last years I was very deep involved in developing DOM, XML, XSL, = XSLT, HTML, and CSS stuff in Java.=20 I ran a server on http://wikiheaven.de, with some wikis on it, i.e. http://www.bigmampf.de.vu. _Some informations about the project..._ I started this project on 17. February 2006, after I spend some days thinking about how nice it would be to produce a better output for a = nicer printing for some documents I had in my wiki. I thought it might be a = good idea if you can use a office product, like Word or OpenOffice Writer, to make a text or article and then put it in a wiki and get such a text, spreadsheet or what ever you want back out of the wiki into your office program, too. So I decided to start a project for creating, storing, writing, = modifying, reading and do what ever you want, with a OpenDocument document. And I started it in PHP, because I wanted to prove, that PHP is much more than = a "server sided script engine" and has the power to do this.=20 Alex Latchford ask me, if this will be a "editor" or solely integrated within MediaWiki. Well, the truth is, I am not sure what it will be in a = few months, but for now your should thing of OpenDocumentPHP as a library. = If you want to make an online editor or make some extensions for wikipedia/MediaWiki, you should be welcome to use OpenDocumentPHP as = your library to access OpenDocuments. That is my personal goal for this = project. When we developed some lines of real code (see POC and stage 1), I will = try to make a application which uses our library to support converting wiki articles in OpenDocuments.=20 _Some informations about POC..._ Because nothing is easy when you start writing a program, I wanted a playground, where I can experiment a little with some of the ideas I had = in mind. So I write a very short "prove of concept" which you all can find = as "/poc" in the Subversion repository at sourceforge.net . It is some = starting point for the whole project. But please take it as it is, only some code from one coder.=20 A teacher of mine always told us, that "programs, are written code from = many people, for many people.", in his lessons. And I think he is right. So = we have to make our own code in the future. This code will go in to "stage = 1".=20 The reason why I published the "/poc" code is simple, not everybody has experiences with "Phing", "PHPUnit2", "PEAR", "XML", and/or "DOM". So I thought a playground for all of us would be nice and we all can learn = what we need. _Some informations about stage 1..._ Having a playground like "POC" is good, but having a goal is even = better. So I like to announce "stage 1", the first real release of OpenDocumentPHP. Goals for "stage 1": * A fine object structure written in UML with at least one fixed interface: OpenDocument and a factory class: OpenDocumentFactory which will give the "customer" a OpenDocument(Single/Package) object. * All classes designed and coded in PHP 5.1.2 or later.. * UnitTests written for PHPUnit2 for all objects in our code base. For a customer it should be possible to get an OpenDocument class form = the factory class, (a single or a package document) and write some stuff to = it, like some lines, some paragraphs, headlines, images, formulas and so on. After the class is filled with some of this stuff, the customer should = get the possibility write this OpenDocument as a file to disk, store it = anywhere else or publish it via HTML as an OpenDocument. I would like to fix the interface for OpenDocument, and any other needed or useful interface in stage 1 as soon as possible, to allow the development of applications = which uses OpenDocumentPHP as soon as possible. There for the documentation of these interfaces and a short guide for it should be one of the first = thinks need to be done in stage 1 next to the code development. Goals for "stage 2 and later" (headword only): * Better ZIP file handling * Less memory consumption (don't held all OpenDocuments in memory, only needed parts) * Faster code (maybe some code parts should be written in C ?) * split up developing and production code. (Get a PEAR::Log free version, to run faster in production, this version should be generated = by Phing "on the fly" from the code base) * Read OpenDocuments, (We should be able to read an existing OpenDocument, and modify it.) * More options to manipulate OpenDocuments. * Help for CSS <-> OpenDocument styles conversion. =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D = =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D = =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D = =3D=20 |
