Age | Commit message (Collapse) | Author | Files | Lines |
|
I'm going to be adding another button down here in the btn-group (more
later). So to make room, I'm removing the text on these buttons,
leaving only the icons. The text will instead be a tooltip, visible
when the button is hovered.
In the case of the 'Close issue' button, it is changed from btn-success
to btn-default. I will tweak colors once this portion of the UI
matures. For now, I don't want the rainbow in my face.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
|
|
Adds 'image/x-ms-bmp' as an allowed mimetype for images, and is
equivalent to 'image/bmp'. The image module is also updated to expect
this new type.
I found an image of mine that, when uploaded, PHP thought was
'image/bmp', so it was allowed. However, when cropping, PHP though it
was 'image/x-ms-bmp' and failed to lookup a loading/writing function.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Adds 'image/bmp' as an allowed mimetype for images. The image module is
also updated to expect this new type.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Adds 'image/gif' as an allowed mimetype for images. The image module is
also updated to expect this new type. For background images, animated
gifs will work properly. For head images, the cropping process
truncates the image to only one frame; this is probably for the best.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
|
|
In preparation for the release, I'm renaming this directory since
'examples' is confusion and misleading. Really this directory just
holds some old code that needs re-integrated, so I name it 'todo'.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
There is not any markdown in this file. Rename it just to a plain .txt
file.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
This was left in a messy state. I'm just cleaning it up a little bit
for now for the release.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Since there is currently no way to set heads for these objects, I am
replacing them with the appropriate glyphicon.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
These text fields need a default of NULL aparently.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Previously, when the app was asked for non-existant paths, no content
was returned and a blank page was presented to the user. Now a canned
message stating that the requested page does not exist is shown, along
with a helpful link back to the Dashboard page.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Since this form submits a file upload, we need it to be set
enctype="multipart/form-data".
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Submissions to the iss-mesg-add form are now handled by this function.
User must be logged in and permitted to post to the issue in question.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
The SQL query here, as written, was omitting 'log' type messages from
the results.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Listing all message (and log messages) beneath the OP in chrono order.
There is a form at the bottom to submit new messages.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Some form handlers use the current logged in user (user::getCurrent()),
however do so without asserting that we are _actually_ logged in. This
is probably due to that fact that index.php (usually) catches all page
requests that are logged out and diverts control before any other handler
can be invoked. But a few handlers sneak through the cracks.
In the future, the app will be better about supportting logged out
browsing, the alpha was not written with this in the forground.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
POSTs to the dm-issue-add form are handled by this new handler. Pad
data is passed via the form, we create the new issue in the pad's first
stage, crediting the current logged in user. New issue is unassigned.
I call `location()` at the bottom, since not doing so leaves the page in
a weird state. The reason being that most of the page rendering logic
operates off of the 'pageObj', which is instanciated and assigned prior
to the invocation of this handler. This is to be fleshed-out during the
v0.2-v0.3 development iteration.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
First button added to the header of pad views is to open new issues.
This interface is still very crude and subject to change in the near
future.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
When viewing a pad, offer the 'New Issue' option under the additions
menu in the navbar. Will will display the just-added new issue modal,
for the user to open a new issue on the first stage of the pad being
viewed.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
This datamods modal is accessable from pad views to open a new issue on
the pad in question. This is a simplistic version of this interface,
subject to improvements once I start on the v0.2-v0.3 development
iteration. Suffice it to say, any frills we will want to use in the
initial draft will be accessible from the issue view modal, as options
to modify the open issue.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Adds a parameterized text area to the collection of controls.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Updated the javascript to wire-up the issue list items shown on pad
views. When these are clicked the associated issue modal is displayed
in the foreground.
|
|
This logic instanciates an issue modal view for each issue to be
accessable from a pad view.
|
|
|
|
|
|
This reverts commit 62872702dc413b7abab94d8a5a7bd21770b5d241.
|
|
|
|
Revised implementation of redesigned data model.
|
|
I found myself complicating the data model of this class of objects and
wanted to take a clean approach to its design. The key differences are
as follows:
* We now reference a message object for the issue's OP, as
opposed to directly containing the message data
This affords the OP _all_ of the standard features of a Scrott
message, including separately tracked authorship data, file
attachments.
* Multiple assignees is implemented in the design
Finally.
* Seen flag is removed
This can be implicitly tracked via all sub-object messages and
the views meta-table.
|
|
This function is patched to co-operate with structural changes to the
issue class.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A dependency loop exists between class/agent.class.php and
class/group.class.php. Due to specific `require_once` ordering within
the app, this problem was not surfaced until now.
These two classes depend on eachother, but strictly speaking, the
interpreter needs to read the agent class first. This is because group
directly inherits from agent. It is only one of agent's functions which
references group. Group has a `require_once "class/agent.class.php"` at
its top, so requiring group first will read both classes, in the correct
order, and provide their definition's for the remainder of the runtime.
The main entry-point, index.php, did not have this problem since it was
explicitly requiring group itself (it actually needs group, though).
The df.php entry-point wasn't and was relying on requires in the class/
directory to resolve this issue. In a more-sane language, I could patch
this more easily directly in the affected file; rather, this patch
updates the df entry-point to explicitly require group, solving the
issue up front.
Hopefully this can be fleshed out in the future as it should not consern
the entry-points that this specific evaluation order needs to take
place.
The third and final entry-point, cron.php, is already fine at the time
of this commit. Its require tree is much simplier, and does not even
include either of the affected classes.
|
|
|
|
This is probabally more of an oops than a bug, although was causing
unexpected behavior.
When falling back to checking whether the agent has access to the
object's owner, it was wrongly accessing through $this->owner, rather
than $obj->owner (which is the function argument). This was probabally
left over from how this function _used_ to be implemented (you would
call on the object and pass in the user).
|
|
|