Messages

1

Ideas / Re: use the newly released google closeure library for editing documents

« on: November 10, 2009, 09:42:49 am »

Our editor can be configured to treat ENTER as a regular line feed instead of a new paragraph. In fact, when composing an email ENTER behaves like that. Do you think it should also behave that way for documents?

Yes, I defenatly do.  If your editing a document, it's the behavior you'd expect.


This is going slightly off topic, looking over the page it looks to be considerably more basic than I was led to believe.  Got the link from an article talking about their document editor along with a link to the now open source library.

2

Ideas / Re: use the newly released google closeure library for editing documents

« on: November 10, 2009, 04:52:58 am »

Yeah it's more than likely missing import/export, but in my experience the editor your using now is very html based, it doesn't have the text document "feel" to it.  Enter does what a linefeed would in html, not what it would do in a text document, etc.

We are on the web, aren't we? It must be HTML based.
I think the key to enhance it is the export functionality, not the editor itself.

Of course you can have XML instead of HTML, but HTML is easier when we are working on the web.

We are on the web, but that doesn't mean it must feel like a web document/web editor.  For example in a document enter would mean linefeed, in the web based editor shift+enter is a linefeed.  It's not much, but it's small things like that that make it seem like your editing a web page and not a document.

3

Ideas / Re: use the newly released google closeure library for editing documents

« on: November 10, 2009, 03:15:55 am »

Yeah it's more than likely missing import/export, but in my experience the editor your using now is very html based, it doesn't have the text document "feel" to it.  Enter does what a linefeed would in html, not what it would do in a text document, etc.

Now of course it depends entirely on how much of the editor is actually there, and I seriously doubt it's much more than a basic rtf editor.  It'd be very cool if it had tables support though.

4

Ideas / use the newly released google closeure library for editing documents

« on: November 08, 2009, 07:30:29 am »

http://closure-library.googlecode.com/svn/trunk/closure/goog/docs/index.html

Now I haven't looked into the specifics, but from the screenshot and text it looks like the normal google docs editor.

It even has "table" and "insert" as menu items.

5

Older versions / Re: [1.5.3+1.6 beta1] Template -> Task -> edit task fails

« on: October 28, 2009, 06:18:11 am »

Great, thank you very much

6

Older versions / Re: [1.5.3+1.6 beta1] Template -> Task -> edit task fails

« on: October 27, 2009, 04:29:16 am »

Try replacing line 112 of '/application/views/task/add_task.php' with this one

Code: [Select]

<?php echo '<div style="float:left;">' .select_project2('task[project_id]', $project instanceof Project ? $project->getId() : 0, $genid) .'</div>'?>


Get the same error with that fix, and with and without the fix most of the options (like tags, task data etc) dont show up at all, so I think there's a different underlaying problem here.

7

Older versions / Re: [1.5.3+1.6 beta1] Template -> Task -> edit task fails

« on: October 26, 2009, 10:21:44 am »

It seems with debug mode on, I can load the screen but clicking on the different options do nothing (except from workspace, which produces the error above).

8

Older versions / Re: [1.5.3+1.6 beta1] Template -> Task -> edit task fails

« on: October 26, 2009, 10:20:33 am »

Can you enable the debug mode?
With debug mode enabled, a detailed error message will be shown instead of the error 500, it will be easier for us to find the problem if you provide us the error message shown when you try to edit.

With debug mode enabled I dont get the same error actually.  However, when pulling up the screen and clicking on different sub options in the task, for example workspace complains about this:

Fatal error: Call to a member function getId() on a non-object in /home/opengoobeta/public_html/application/views/task/add_task.php on line 112

As I've seen this on clean installs of 1.5.3 I figured it was easily reproduced, hence the lack of a log in the original report.

We shall improve it greatly soon, because we see that it is very useful for many people but it now has some limitations.

Even with it's limited features it's a VERY handy tool.  I use it to create a bunch of tasks and milestones associated with starting new projects / taking in new clients for example.

9

Older versions / [1.5.3+1.6 beta1] Template -> Task -> edit task fails

« on: October 26, 2009, 06:09:08 am »

If you create a template with some tasks, then go into the template, click a task and attempt to edit it you'll get 500 internal server error.

I'm also a bit unsure on how I'm supposed to "organize" tasks in templates.  I'd like to be able to continue to update them/organize them/edit them, but I'm unsure where to put them.

I might just make a workspace called templates and archive it as that's possible now, but I'm not sure if that part of the template system is thought through?

10

Older versions / [1.6 Beta1] Upgrade script missing a permission check.

« on: October 26, 2009, 05:18:52 am »

file config/installed_version.php has to be writable, it only checks config.php + the config directory.

11

Ideas / Re: Archive data?

« on: October 14, 2009, 03:29:39 am »

Most the discussion I found around it was based on archiving workspaces, which is good and something I need, but archiving documents for me is far more urgent.  I see this feature as something discussed since 1.2 so I hope it hasn't been forgotten :/

12

Feature requests / Re: Archive workspace

« on: October 14, 2009, 03:25:22 am »

I currently solve this by having two major categories, one called Active and one called Ended, it's not as clean as an archive system would be, but it sortof works.

13

Ideas / Archive data?

« on: October 13, 2009, 04:00:36 am »

I get a lot of information from different sources, and in time I make one updated document which merges and organizes this information.  I'd love to be able to link that document to the old data (and I can), and then archive it.

I need the raw data so I'm able to document directly what was said/logged, but I dont want it available at all time.

Maybe a archive tag which is hidden by default?

// edit, and on that subject it'd be nice with a "Untagged" tag as well, to see data that isn't tagged yet.